Systems and methods for remotely determining a battery characteristic

ABSTRACT

Included are embodiments for remotely determining a battery characteristic. Some embodiments include searching for a first wireless signal that identifies the energy storage device and, in response to receiving the first wireless signal, determining a current charge level of the energy storage device. Some embodiments include receiving a second wireless signal from the energy storage device, determining from the second wireless signal, whether the current charge level of the energy storage device reaches a predetermined threshold, and in response to determining that the current charge level of the energy storage device reaches the predetermined threshold, facilitating replacement of the battery.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 16/572,520 filed Sep. 16, 2019, which is a continuation of U.S. Ser. No. 15/950,911 filed Apr. 11, 2018, which is a continuation of U.S. Ser. No. 15/660,565 filed Jul. 26, 2017, which is a continuation of U.S. Ser. No. 14/259,677, filed Apr. 23, 2014, which claims priority to U.S. Ser. No. 61/837,879, filed Jun. 21, 2013, the entire disclosures of each of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present application relates generally to systems and methods for remotely determining a battery characteristic and specifically to utilize wireless communications to determine charge level and/or health of a battery or other energy storage device.

BACKGROUND OF THE INVENTION

Many electric devices rely on battery power to provide a greater level of mobility and freedom from power chords. While battery-operated devices are becoming more desired, oftentimes a battery charge may deplete during use, thereby limiting the effectiveness of the device. This can create inconveniences due to the unexpected nature of the battery failure and the uncertainty of locating replacement batteries. As a consequence, many battery-powered devices become less convenient in these respects, due to these and other limitations.

SUMMARY OF THE INVENTION

Included are embodiments for remotely determining a battery characteristic. Some embodiments include searching for a first wireless signal that identifies the energy storage device and, in response to receiving the first wireless signal, determining a current charge level of the energy storage device. Some embodiments include receiving a second wireless signal from the energy storage device, determining from the second wireless signal, whether the current charge level of the energy storage device reaches a predetermined threshold, and in response to determining that the current charge level of the energy storage device reaches the predetermined threshold, sending, by the computing device, an alert indicating the current charge level.

Also included are embodiments of a computing device. Some embodiments of the computing device include a processor and a memory component. The memory component may store logic that, when executed by the processor, causes the computing device to detect a wireless communication signal from a battery, determine, from the wireless communication signal, a battery characteristic of the battery, and provide a first user interface that includes data related to the battery characteristic of the battery.

Also included are embodiments of a non-transitory computer-readable medium. Some embodiments of the non-transitory computer-readable medium include logic that, when executed by a computing device, causes the computing device to determine whether an unused or partially used energy storage device is available and within a predetermined range. In response to determining that the unused or partially used energy storage device is available and within the predetermined range, the logic may cause the computing device to determine whether the unused or partially used energy storage device is compatible with a device that the energy storage device currently powers, and in response to determining that the unused or partially used energy storage device is compatible with the device that the energy storage device currently powers, provide a second user interface that includes a physical location of the energy storage device. In some embodiments, in response to determining that no unused energy storage devices are available and within the predetermined range, the logic causes the computing device to facilitate an online purchase of a replacement energy storage device.

BRIEF DESCRIPTION OF THE DRAWINGS

It is to be understood that both the foregoing general description and the following detailed description describe various embodiments and are intended to provide an overview or framework for understanding the nature and character of the claimed subject matter. The accompanying drawings are included to provide a further understanding of the various embodiments, and are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments described herein, and together with the description serve to explain the principles and operations of the claimed subject matter.

FIG. 1 depicts a computing environment for remotely determining a battery characteristic, according to embodiments disclosed herein;

FIG. 2 depicts a user computing device that may be utilized for remotely determining a battery characteristic, according to embodiments disclosed herein;

FIG. 3 depicts a user interface for searching for batteries and/or devices, according to embodiments disclosed herein;

FIG. 4 depicts a user interface for providing a list of located batteries, according to embodiments disclosed herein;

FIG. 5 depicts a user interface for providing battery level of batteries that power a device, according to embodiments disclosed herein;

FIG. 6 depicts a user interface for providing a battery level for a particular battery that powers a device, according to embodiments disclosed herein;

FIG. 7 depicts a user interface for recommending a battery replacement strategy, according to embodiments disclosed herein;

FIG. 8 depicts a user interface for identifying that replacement batteries have been inserted into a device, according to embodiments disclosed herein;

FIG. 9 depicts a user interface for providing a list of located battery-operated devices, according to embodiments disclosed herein;

FIG. 10 depicts a user interface for adding a device for monitoring, according to embodiments disclosed herein; and

FIG. 11 depicts a flowchart illustrating a process that may be utilized for remotely determining a battery characteristic.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments disclosed herein include systems and methods for remotely determining a battery characteristic. Specifically, embodiments disclosed herein include a user computing device, such as a mobile telephone, tablet computer, a near field communication (NFC) reader, etc., that is configured for wirelessly receiving a wireless communication signal from a powered device, a battery, and/or other energy storage device (broadly referred to herein as a “battery”). The user computing device may be incorporated within a device, such as a television, an automobile, etc. The battery may include a radio frequency identifier (RFID) tag, wireless fidelity (Wi-Fi) transmitter, Bluetooth transmitter, a barcode, and/or other wireless communicator for communicating with the computing device. The user computing device may exchange data with the battery (and/or device that the battery currently powers) for monitoring a characteristic of the battery, such as a current impedance level, a current charge level, a current depletion rate, etc.

Similarly, some embodiments may be configured such that the user computing device communicates with the powered device that is powered by the battery. In such embodiments, the powered device may then communicate with the battery and/or may include testing hardware for determining the characteristic of the battery. The powered device may communicate information about the usage frequency of the device or other information about the powered device. The user computing device may provide the user with usage suggestions as a result of the information communicated to the user computing device from the powered device. Other embodiments are also within the scope of this disclosure and are described in detail, below.

Referring now to the drawings, FIG. 1 depicts a computing environment for remotely determining a battery characteristic, according to embodiments disclosed herein. As illustrated, a network 100 may be coupled to a user computing device 102, a remote computing device 104, a battery 106, and/or a powered device 108. As also shown, the powered device 108 may be coupled with a different battery 110. The network 100 may include any wide area and/or local area network, such as the internet, a mobile communications network, a satellite network, a public service telephone network (PSTN) and/or other network for facilitating communication between devices. If the network 100 includes a local area network, the local area network may be configured as a communication path via Wi-Fi, Bluetooth, RFID, and/or other wireless protocol.

Accordingly, the user computing device 102 may include a personal computer, laptop computer, tablet, mobile communications device, database, and/or other computing device that is accessible by a user. The user computing device 102 may additionally include a memory component 140, which stores data capturing logic 144 a and interface logic 144 b, described in more detail below.

The remote computing device 104 is also coupled to the network 100 and may be configured as an online retailer for purchasing additional batteries, as an information server for accessing data regarding the battery 106, a data collection server for monitoring battery usage and useful life, etc., as described in more detail, below. As an example, the user computing device 102 may recognize that a charge level of a disposable battery or a health of a rechargeable battery that indicates an expected time that the battery should be replaced. As described in more detail below, the user computing device 102 may communicate with the remote computing device 104 to order replacement batteries (or other replacement energy storage device).

Similarly, a battery manufacturer may monitor use of battery life and usage for designing new batteries. In addition, or alternatively, the battery manufacturer may monitor manufacturing and quality-related data of the battery, such as via the remote computing device 104. In such embodiments, the remote computing device 104 may function as a server for collecting and analyzing such data. In some embodiments, the remote computing device 104 may provide a user account for a battery purchaser to monitor battery usage from any computing device with access to the network 100.

Also depicted in FIG. 1 is a battery 106. The battery 106 may take the form of any energy storage device, such as a chemical battery (such as an alkaline primary battery, a lithium primary battery, a nickel-metal hydride rechargeable battery, a lithium ion rechargeable battery, etc.), a dry cell, wet cell, capacitor, and/or others. Regardless of the type of energy storage device, the battery 106 may be configured with one or more sensors for determining a battery characteristic (or a plurality of battery characteristics). The battery characteristics may include a current charge level; a depletion rate; an impedance; an open-circuit voltage (OCV); a closed-circuit voltage; a discharge rate; discharge/charge cycles; cycle life; a battery type, such as primary or secondary; a battery size, such as AAA, AA, C, or D; an end of battery life; battery manufacturing/quality-related data, such as manufacturing date, material lot number, cell assembly line number, active material weights, electrolyte weights, and any other manufacturing-related information; etc. Additionally, the battery 106 may include a wireless transmitter, such as an RFID tag, Bluetooth transmitter, Wi-Fi transmitter, etc. for sending data to the user computing device 102 and/or the remote computing device 104. The wireless transmitter may be installed with the battery during manufacturing and/or applied after the battery is manufactured. The data may include the battery characteristics, a battery identifier, a powered device identifier, location information, a physical location, and/or other information.

While the battery 106 is depicted as not powering a powered device, this is merely an example. As discussed in more detail below, the user computing device 102 and/or the remote computing device 104 may be configured to communicate with batteries that are powering devices, unused, and/or partially used, but not currently powering a powered device. As such, the battery 106 may or may not be currently powering a powered device. Similarly, the battery 106 may or may not be currently charged by a battery charging device.

Additionally depicted in FIG. 1 is a powered device 108 that communicates with the user computing device 102 and/or the remote computing device 104. Specifically, while some embodiments disclosed herein may include a battery 106 that is configured for sending wireless signals to the user computing device 102 and/or the remote computing device 104, this is merely an example. Specifically, the battery 110 may power the powered device 108 and thus may be electrically coupled with the powered device 108. Accordingly, the powered device 108 may be configured to communicate information with the battery 110, such that in response to the powered device 108 receiving a battery characteristic and/or other data, the powered device 108 may communicate with the user computing device 102 and/or the remote computing device 104, as described above. Such an embodiment accommodates situations where the battery 110 does not include a wireless transmitter. Similarly, some embodiments may be configured such that the powered device 108 includes one or more sensors for determining the battery characteristic, as well as logic for determining a battery identifier.

It should also be understood that while the user computing device 102 and the remote computing device 104 are each depicted as individual devices, these are merely examples. Either of these devices may include one or more personal computers, servers, laptops, tablets, mobile computing devices, data storage devices, mobile phones, etc. that are configured for providing the functionality described herein. It should additionally be understood that other computing devices may also be included in the embodiment of FIG. 1.

Similarly, while single batteries 106 and 110, as well as a single powered device 108 are depicted in FIG. 1, this is also merely an example. As is understood, a plurality of batteries (or a plurality of energy storage devices) may power a device, such as powered device 108. Accordingly, the user computing device 102 and/or the remote computing device 104 may be configured to communicate with a plurality of different batteries, powering a plurality of different devices, and/or not currently associated with a device.

FIG. 2 depicts a user computing device 102 that may be utilized for remotely determining a battery characteristic, according to embodiments disclosed herein. In the illustrated embodiment, the user computing device 102 includes a processor 230, input/output hardware 232, network interface hardware 234, a data storage component 236 (which stores battery data 238 a and device data 238 b), and the memory component 140. The memory component 140 includes hardware and may be configured as volatile and/or nonvolatile memory and, as such, may include random access memory (including SRAM, DRAM, and/or other types of RAM), flash memory, registers, compact discs (CD), digital versatile discs (DVD), and/or other types of non-transitory computer-readable mediums. Depending on the particular embodiment, the non-transitory computer-readable medium may reside within the user computing device 102 and/or external to the user computing device 102.

Additionally, the memory component 140 may be configured to store operating logic 242, the data capturing logic 144 a, and the interface logic 144 b, each of which may be embodied as a computer program, firmware, and/or hardware, as an example. A local communications interface 246 is also included in FIG. 2 and may be implemented as a bus or other interface to facilitate communication among the components of the user computing device 102.

The processor 230 may include any hardware processing component operable to receive and execute instructions (such as from the data storage component 236 and/or memory component 140). The input/output hardware 232 may include and/or be configured to interface with a monitor, keyboard, mouse, printer, camera, microphone, speaker, and/or other device for receiving, sending, and/or presenting data. The network interface hardware 234 may include and/or be configured for communicating with any wired or wireless networking hardware, a satellite, an antenna, a modem, LAN port, wireless fidelity (Wi-Fi) card, RFID receiver, Bluetooth receiver, image recognizer (for recognizing a battery and/or other data related to the battery in place of the other wireless data communication mediums), bar code reader, WiMax card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. From this connection, communication may be facilitated between the user computing device 102, the battery 106, the powered device 108, the remote computing device 104, and/or other computing devices. It should be understood that the data storage component 236 may reside local to and/or remote from the user computing device 102 and may be configured to store one or more pieces of data for access by the user computing device 102 and/or other components. In some embodiments, the data storage component 236 may be located remotely from the user computing device 102 and thus accessible via the network 100. In some embodiments however, the data storage component 236 may merely be a peripheral device, but external to the user computing device 102.

Included in the memory component 140 are the operating logic 242, the data capturing logic 144 a, and the interface logic 144 b. The operating logic 242 may include an operating system and/or other software for managing components of the user computing device 102. Similarly, the data capturing logic 144 a may be configured to cause the user computing device 102 to detect and receive communications from the battery 106 and/or the powered device 108. The interface logic 144 b may cause the user computing device 102 to make determinations from the received data, as well as provide user interfaces, communicate with the remote computing device 104, and/or perform other operations, as discussed below.

It should be understood that the components illustrated in FIG. 2 are merely exemplary and are not intended to limit the scope of this disclosure. While the components in FIG. 2 are illustrated as residing within the user computing device 102, this is merely an example. In some embodiments, one or more of the components may reside external to the user computing device 102.

FIG. 3 depicts a user interface 330 for searching for batteries and/or powered devices, according to embodiments disclosed herein. As illustrated, the user computing device 102 may provide the user interface 330 (and/or other user interfaces described herein). Specifically, the user interface 330 may be provided as part of a software application, such as those downloaded for a mobile telephone or other device. Once the software application is launched (which may be caused by a user input and/or detection of a readable battery or powered device), the user interface 330 may be provided for searching for batteries in the vicinity of the user computing device 102.

As discussed above, the battery 106 and/or the powered device 108 may include a wireless communication mechanism, such as an RFID tag, Wi-Fi transmitter, etc. Accordingly, the user computing device 102 may detect which batteries are within range of the user computing device 102. Similarly, some embodiments may be configured such that the batteries communicate with a device, such as a router or other bridging device that is communicatively coupled to a local network. This device may additionally communicate with the user computing device 102 to allow the user computing device 102 the ability to monitor the batteries and/or devices, even when the user computing device 102 is not within range to communicate directly with the batteries and/or other devices. Such embodiments may serve useful, such as if the user is shopping and cannot remember which batteries need replacing.

Also included in the user interface 330 is a user option, such as a search devices option 332. The search devices option 332 may activate a feature for the user computing device 102 to locate powered devices, instead of batteries. As described above, certain powered devices may be equipped with the ability to communicate battery characteristics with the user computing device 102.

FIG. 4 depicts a user interface 430 for providing located batteries, according to embodiments disclosed herein. In response to the user computing device 102 detecting one or more batteries, the user interface 430 may be provided. As illustrated, the user interface 430 may provide user options, such as battery options 432 a-432 f (collectively referred to as “battery options 432”) of batteries that were located, as well as additional information about the batteries. Such additional information may include a battery type, a powered device type, a physical location, and/or other information. In response to selection of one or more of the battery options 432, additional details may be provided. Also included is a devices option 434. In response to selection of the devices option 434, listing of located powered devices may be provided.

FIG. 5 depicts a user interface 530 for providing battery level of batteries that power a device, according to embodiments disclosed herein. In response to selection of the battery option 432 a from FIG. 4, the user interface 530 may be provided. Specifically, the user interface 530 includes battery condition indicators 532 a, 532 b, and 532 c, which provide a graphical representation of whether the batteries in the remote control should be replaced. The battery condition indicator 532 a signifies that a battery that is in good condition. The battery condition indicator 532 b signifies that a battery is in a warning condition. The battery indicator 532 c signifies that a battery is in a replacement condition. As an example, battery condition indicator 532 a may represent a battery that has 100-67 charge remaining. The battery condition indicator 532 b may represent a battery that has 67-33 charge remaining. The battery indicator 532 c may represent a battery that has 33-0 charge remaining.

Also provided in the user interface 530 are individual battery statuses 534. Specifically, while a particular powered device (such as the remote control depicted in FIG. 5) may utilize a plurality of batteries. As such, all of those batteries may need to have a certain charge level to cause the powered device to operate. However, this does not necessarily mean that all of the batteries need to be replaced. Specifically, if one of the batteries is in poor condition with regard to the other batteries that power the powered device 108, the individual battery statuses 534 may provide this information.

Also included are a view all option 536 and a recommendations option 538. In response to selection of the view all option 536, information related to all of the batteries in the powered device may be provided. In response to selection of the recommendations option 538, recommendations for replacing the batteries may be provided.

FIG. 6 depicts a user interface 630 for providing a battery level for a particular battery that powers a powered device 108, according to embodiments disclosed herein. In response to selection of one of the individual battery statuses 534 from FIG. 5, the user interface 630 may be provided. As illustrated, the user interface 630 includes a graphical representation 632 that includes the battery and a representation of a battery characteristic. Also included are a textual remaining charge indicator 634 a, and a time until replacement indicator 634 b. The user interface 630 may also identify a battery type, as well as another use for the battery in its current condition. Identifying battery type may be utilized to determine authenticated and/or counterfeited branded batteries to determine the authenticity of a battery that is placed in use. Additionally, the identification may be utilized for monitor and crediting a user's proper maintenance of batteries. As an example, the identifier may be coupled with logic described herein to indicate when (and/or where) a battery should be recycled. The consumer recycling habits may be recorded and the user may be provided with coupons, credits, or other incentives for recycling.

Specifically, if the battery is currently being used in a powered device that consumes large amounts of power (such as a camera); the battery may be considered depleted. However, the battery may be capable for use in a different powered device that consumes less power (such as a clock). Accordingly, the user computing device 102 may determine battery usage of the detected powered devices and may recommend an alternative use for the battery. If no alternative use is available, the user computing device 102 may recommend discarding or recharging the battery. Accordingly, a recommendations option 636 is also provided in FIG. 6. In response to selection of the recommendations option 636, other recommendations for the battery may be provided.

It should be understood that the user computing device 102 may be configured to determine a depletion rate of one or more of the batteries. As an example, some embodiments may be configured such that the powered device 108 and/or the battery 106 are configured to determine the depletion rate and send this information to the user computing device 102. As another example, some embodiments may be configured such that the powered device 108 is configured to communicate the device type to the user computing device 102. The user computing device 102 may use the device type in combination with a discharge model stored within the memory of the user computing device 102 to determine the depletion rate. As another example, some embodiments may be configured such that the user computing device 102 includes a device lookup table within its memory. The user may select the powered device 108 from the lookup table and input the selected device into the user computing device 102. The user computing device 102 may use the device type that the user inputs in combination with a discharge model stored within the memory of the user computing device 102 to determine the depletion rate. As another example, the user computing device 102 may include image recognition capabilities. The user may take a picture of the powered device 108 with the user computing device 102. The user computing device 102 may use the device type in combination with a discharge model stored within the memory of the user computing device 102 to determine the depletion rate. Similarly, some embodiments are configured such that the battery (and/or powered device) merely sends the user computing device 102 a first wireless signal that identifies a current charge level. The battery (and/or powered device) may send a second wireless signal at a second time that identifies a charge level at that time. From this information, the user computing device 102 may determine a depletion rate of the battery 106. Additionally, the user computing device 102 may identify an external condition that affects the battery characteristic of the battery 106. As an example, temperature, humidity, and/or other factors may affect depletion rate and/or other characteristics of the battery. Accordingly, the user computing device 102 may account for one or more of these external conditions determine the current depletion rate of the battery. The depletion rate may also be displayed graphically by the user computing device 102. For example, an x-y graph of voltage versus time may be displayed by the user computing device 102 to indicate to the consumer the depletion rate of the battery 106 and/or the battery 110 within the powered device 108.

FIG. 7 depicts a user interface 730 for recommending a battery replacement strategy, according to embodiments disclosed herein. In response to selection of the recommendations option 538 from FIG. 5 and/or the recommendations option 636 from FIG. 6, the user interface 730 may be provided. As illustrated, the user interface 730 includes a physical location of batteries that may be utilized as a replacement battery. Specifically, the user computing device 102 may determine whether a partially used or unused battery (or other unused energy storage device) is available and within a predetermined range (such as in the user's house). As indicated, the batteries may be currently unused batteries, partially used batteries that are not currently in use and/or partially used batteries that are currently in use (such as those that are depleted for their current powered device). Additionally, the user interface 730 includes an unused option 732, a partially used option 734, and a purchase option 736.

In response to selection of the unused option 732, the user is indicating to the user computing device 102 that the replacement batteries will be the unused batteries recommended in the user interface 730. Selection of the partially used option 734 indicates that the partially used batteries will be used. Selection of the purchase option 736 opens another user interface and/or otherwise facilitates purchase of (or directs the user of where to purchase) replacement batteries.

Specifically, some embodiments may be configured to make a prediction regarding an expected time that a battery may deplete to a predetermined charge level. The user computing device 102 may additionally determine whether this predicted time falls within a predetermined timeframe (e.g., such as within two days). Accordingly, embodiments may be configured to, in response to determining that the expected time falls within the predetermined timeframe, facilitate a purchase, for example online or in-store, of a replacement battery. The user computing device 102 may include global positioning system (GPS) capability to direct the consumer to the nearest retail outlet to purchase the replacement battery. The user computing device 102 may connect to an inventory and/or cost database of the retail outlets to enable the user to make an informed decision as to which retail outlet to purchase the replacement battery. The user computing device 102 may also recommend a method of disposal or a method of recycling a depleted battery.

Similarly, some embodiments may be configured to determine whether a battery has entered a retail establishment. If so, the user computing device 102 may be provided with a coupon or discount for replacing that battery (such as during that visit). Additional discounts and/or digital marketing may be provided to the user, based on pick lists, guiding questions, user profile information, and/or other information about the user.

FIG. 8 depicts a user interface 830 for identifying that replacement batteries have been inserted into a device, according to embodiments disclosed herein. In response to selection of the unused option 732 from FIG. 7, the user interface 830 may be provided. As illustrated, the user interface 830 includes a statement of the selected batteries, as well as an inserted option 832, a back option 834, and a devices option 836. Once the user has inserted the replacement batteries into the powered device, the user may select the inserted option 832, so the user computing device 102 may begin acquiring data regarding this new use. Selection of the back option 834 returns the user to the user interface 730 from FIG. 7 to reselect the batteries that will be used. Selection of the devices option 836 allows the user to view other detected powered devices. It will be understood that while the user may manually provide the user input discussed with regard to FIGS. 7 and 8, this is merely an example. Specifically, some embodiments may be configured to automatically detect the batteries that are inserted into a powered device. In such embodiments, the user need not select the batteries that will be inserted or indicate when the batteries are inserted into the powered device.

FIG. 9 depicts a user interface 930 for providing located battery-operated devices, according to embodiments disclosed herein. In response to selection of the search devices option 332 from FIG. 3 and/or the devices option 434 from FIG. 4, the user interface 930 may be provided. As discussed above, the user computing device 102 may search for batteries and/or powered devices. Accordingly the user interface 930 may provide device options 932 a-932 g. In response to selection of one of the device options 932 a-932 g, additional information regarding the powered device and/or the batteries that power the powered device may be provided. As an example, the user computing device 102 may predict a time frame for the battery to deplete to a predetermined charge level. This information may be provided in the user interface 930. Also included in the user interface 930 is an add device option 934. The add device option 934 provides the user with the ability to manually add a device that may have otherwise not been detected, as described in more detail below. The user computing device 102 may include image recognition capabilities. The user may take a picture of the powered device with the user computing device 102. The picture, or other image, of the powered device may be associated with the powered device. The picture, or other image, of the powered device may be provided in the user interface 930.

FIG. 10 depicts a user interface 1030 for adding a device for monitoring, according to embodiments disclosed herein. In response to selection of the add device option 934 from FIG. 9, the user interface 1030 may be provided. As illustrated, the user interface 1030 may include a device name option 1032, a device type option 1034, a device brand option 1036, and a battery type option 1038. In response to selection of the device name option 1032, the user may input a device name for the new device. In response to selection of the device type option 1034, the user may input a device type. In response to selection of the device brand option 1036 the user may input a brand of the device, a model number, and/or other similar data. In response to selection of the battery type option 1038, the user may input the size of the battery that the powered device receives and/or other similar data. The user computing device 102 may include image recognition capabilities. The user may take a picture of the device with the user computing device 102. The picture, or other image, of the device may be associated with the powered device. The picture, or other image, of the powered device may be provided in the user interface 1030.

FIG. 11 depicts a flowchart illustrating a process that may be utilized for remotely determining a battery characteristic. As illustrated in block 1150, a search may be performed for a first wireless signal (an incoming wireless signal) that identifies an energy storage device. In block 1152, in response to receiving the first wireless signal, a characteristic of the energy storage device may be determined. In block 1154, a second wireless signal may be received from the energy storage device. In block 1156, a determination may be made, from the second electrical signal, whether the characteristic of the energy storage device reaches a predetermined threshold. This determination may include determining whether the battery charge is depleted beyond a predetermined threshold. Other examples include scenarios where the impedance changes beyond a predetermined threshold, whether battery charge depletes at a rate beyond a predetermined threshold, etc. In block 1158, in response to determining that the characteristic of the energy storage device reaches the predetermined threshold, an alert may be sent indicating the characteristic.

The dimensions and values disclosed herein are not to be understood as being strictly limited to the exact numerical values recited. Instead, unless otherwise specified, each such dimension is intended to mean both the recited value and a functionally equivalent range surrounding that value. For example, a dimension disclosed as “40 mm” is intended to mean “about 40 mm.”

Every document cited herein, including any cross referenced or related patent or and any patent application or patent to which this application claims priority or benefit thereof, is hereby incorporated herein by reference in its entirety unless expressly excluded or otherwise limited. The citation of any document is not an admission that it is prior art with respect to any invention disclosed or claimed herein or that it alone, or in any combination with any other reference or references, teaches, suggests or discloses any such invention. Further, to the extent that any meaning or definition of a term in this document conflicts with any meaning or definition of the same term in a document incorporated by reference, the meaning or definition assigned to that term in this document shall govern.

While particular embodiments of the present invention have been illustrated and described, it would be obvious to those skilled in the art that various other changes and modifications can be made without departing from the spirit and scope of the invention. It is therefore intended to cover in the appended claims all such changes and modifications that are within the scope of this invention. 

What is claimed is:
 1. A computing device for remotely monitoring battery activity comprising: a processor; and a non-transitory memory component that stores logic that, when executed by the processor, causes the computing device to perform at least the following: detect a wireless communication that identifies a battery; determine, from the wireless communication signal, a battery characteristic of the battery; provide, via a user interface generated by a software application executing on the computing device, data related to the battery characteristic of the battery; predict a charge remaining in the battery; determine that an unused or partially used battery is within a signal range of the computing device; in response to determining that the unused or partially used battery is within the signal range of the computing device, provide, via a user interface generated by the software application executing on the computing device, an indication of a physical location of the unused or partially used battery.
 2. The computing device of claim 1, wherein the signal range of the computing device is a Bluetooth signal range.
 3. The computing device of claim 1, wherein the logic further causes the computing device to determine a current depletion rate of the battery.
 4. The computing device of claim 3, wherein to determine the current depletion rate of the battery, the logic further causes the computing device to: access a discharge model stored in a memory of the computing device.
 5. The computing device of claim 1, wherein the logic further causes the computing device to: search for the battery upon launching the software application, and detect the wireless communication in response to the search.
 6. The computing device of claim 1, wherein the logic further causes the computing device to predict an expected time when the battery will be depleted.
 7. The computing device of claim 1, wherein the logic further causes the computing device to transmit the charge remaining in the battery to a remote server associated with a manufacturer of the battery.
 8. A method for remotely monitoring activity of an energy storage device, comprising: searching, by a computing device, for a first wireless signal that identifies the energy storage device; in response to detecting the first wireless signal, determining, by the computing device, a current charge level of the energy storage device; receiving, by the computing device, a second wireless signal from the energy storage device; based on the second wireless signal, determining, by the computing device, that the current charge level of the energy storage device is depleted below a threshold charge level; in response to determining that the current charge level of the energy storage device is depleted below the threshold charge level, generating, by the computing device, an alert indicating that the current charge level is depleted below the threshold charge level; determining that an unused or partially used energy storage device is within a signal range of the computing device; and in response to determining that the unused or partially used energy storage device is within the signal range of the communication device, providing a user interface that includes a physical location of the unused or partially used energy storage device.
 9. The method of claim 8, further comprising predicting a time that the current charge level will reach the threshold charge level.
 10. The method of claim 8, wherein the signal range of the computing device is a Bluetooth signal range.
 11. The method of claim 8, further comprising: transmitting the current charge level of the energy storage device to a remote server associated with a manufacturer of the energy storage device.
 12. The method of claim 8, wherein the computing device searches for the first wireless signal in response to launching a software application.
 13. The method of claim 8, further comprising receiving location information of a plurality of energy storage devices that are located within the signal range of the computing device.
 14. The method of claim 8, further comprising: predicting an expected time when the energy storage device will be depleted.
 15. The method of claim 14, wherein predicting the expecting time when the energy storage device will be depleted comprises: access a discharge model stored in a memory of the computing device.
 16. A non-transitory computer-readable medium for remotely monitoring activity of an energy storage device powering a powered device that stores logic that, when executed by a processor, causes a computing device to perform the following: search for a first wireless signal that identifies the energy storage device; in response to detecting the first wireless signal, determine a current charge level of the energy storage device; receive a second wireless signal from the energy storage device; based on the second wireless signal, determine that the current charge level of the energy storage device is depleted below a threshold charge level; in response to determining that the current charge level of the energy storage device is depleted below the threshold charge level, generate an alert indicating that the current charge level is depleted below the threshold charge level; determine that an unused or partially used energy storage device is within a signal range of the computing device; and in response to determining that the unused or partially used energy storage device is within the signal range of the communication device, providing a user interface that includes a physical location of the unused or partially used energy storage device.
 17. The non-transitory computer-readable medium of claim 16, wherein the signal range of the computing device is a Bluetooth signal range.
 18. The non-transitory computer-readable medium of claim 16, wherein the logic causes the computing device to: transmit the current charge level of the energy storage device to a remote server associated with a manufacturer of the energy storage device.
 19. The non-transitory computer-readable medium of claim 16, wherein the logic causes the computing device to search for the first wireless signal in response to launching a software application.
 20. The non-transitory computer-readable medium of claim 16 wherein the logic causes the computing device to receive location information of a plurality of energy storage devices that are located within the signal range of the computing device. 